Method, apparatus and computer program to provide access to client records and data resources

ABSTRACT

A method, computer program and apparatus are disclosed that include accessing client data records, such as, medical records. The method for may include, for example, receiving a data file at a file server comprising client records information. The method may also include forwarding the file to a database and adding the file to a record in the database, creating a database file and storing the database file on the file server, and scheduling a call to at least one client, the call including a portion of the information included in the received data file. The method may further provide performing the call, monitoring the call, and may also include updating the client records information stored in the database based on the additional information provided by the at least one client.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation from U.S. patent application Ser. No.15/145,200, filed May 3, 2016, entitled “METHOD, APPARATUS AND COMPUTERPROGRAM TO PROVIDE ACCESS TO CLIENT RECORDS AND DATA”, which is acontinuation from U.S. patent application Ser. No. 12/758,936, filedApr. 13, 2010, entitled “METHOD, APPARATUS AND COMPUTER PROGRAM TOPROVIDE ACCESS TO CLIENT RECORDS AND DATA”, now issued U.S. Pat. No.9,330,234, the entire contents of each of which are incorporated byreference herein in their entirety.

FIELD OF THE INVENTION

The present inventive concept is related to a data records configurationthat allows clients to access their personal data records and to receiveupdated information pertaining to their personal records information.

BACKGROUND OF THE INVENTION

Conventional data record systems that provide client access to theirpersonal records may be provided by a variety of different mediums andnetworking systems. One example of a data record system may be atelephony-based system which allows clients to access their personalrecord information by operating a telephone. For instance, a client maywish to access personal medical records stored in a remote database bycalling a phone-based data record system and accessing their records viakeypad entries or voice commands made over their telephones.

The telephony-based data record systems may provide access to clientrecords through a remote web server and a corresponding database. Forexample, FIG. 1 illustrates a conventional data record accessing system10A. Referring to FIG. 1, client 100 uses a hypertext transfer protocolscript secure (HTTPS) web posting application to connect to a web server101 over the network, which is illustrated by the network cloud that mayrepresent a wide area network, the Internet, etc. Once a connection isestablished the client may send a data file to the web server 101.

The data file is originally sent to the web server 101 which provides aconnection to a file server 102. After the file has been moved to thefile server 102, a record is generated based on the received file, andthat record is sent to a database server, such as, for example, a SQLserver 103. The SQL server 103 receives the data file and a record maybe generated and added to the SQL database in the SQL server 103.

The file server 102 includes two server engines, which include a parserserver engine 102A and an image parser engine 102B. These file serverengines provide additional features for processing the data files whichare sent to the file server 102. For example, parser server 102A mayread and write the data files to the SQL cluster at the SQL server 103.Other applications performed by the file server 102 may include filebranding, storing and accessing of appointment file information andvoice files (i.e., VCE files).

The SQL sever 103 may also provide additional applications, such as, aparse queue to parse data received from the data file, appointment dataorganization and storage, email applications for sending reminders toindividuals including bulk email, news letter creation and updatingprocedures, after hours data access services for clients, and shortmessaging services (SMS) for clients.

The parser server 102A may also parse information for the client, suchas, appointment data, and then format the appointment data for storagein appointment tables. The image parser may obtain image informationstored in a remote storage unit 104, which may be a database ofpre-stored data records, for example, dental records, medical records,x-rays, client chart information, etc.

After data has been stored and processed by the data record accessingsystem 10A, the clients may access the data records by using an internetportal link to connect to the web server 101 and access client datarecords. For example, a client may access pre-stored records to obtainappointment information of an approaching doctor appointment based onclient data records previously stored in the appointment tables by thefile server 102 and the parser server 102A.

Upon accessing the client's records, certain information may be providedautomatically or in response to a request submitted by the clientaccessing the client's records. For instance, images that are stored inthe storage 104 and that are associated with the client's personal datamay be offered to the client and downloaded to the client's terminaldevice (not shown).

A similar access scheme may be performed by a client calling in over atelephone to a telephone server 106, which includes an engine 106A and avoice board 106B. For example, after the offices are closed, clients maydesire to access their personal data records so that certain informationmay be confirmed, such as, their appointment time for their next doctorvisit.

The engine 106A and the voice board 106B provide the clients with thenecessary options to access their personal information. The client mayaccess appointment information and pre-recorded voice file (VCE)information from the file server 102 regarding personal recordinformation. In addition, the telephone server 106 may provide anemergency service that calls the clients when their related personalmedical information requires immediate attention. The emergencynotifications may also be provided by e-mail, text messaging and othernotification techniques via the e-mail server 105.

The conventional data record accessing system 10A performs data recordstorage and accessing options without anticipating changes to theclients' needs and without providing a dynamic updating platform.Clients need access to all of their personal records, and also need toupdate their personal records based on the changes that may occur sincetheir last information accessing session and/or during their currentsessions with the data record assessing system.

SUMMARY OF THE INVENTION

Disclosed is an optimized method, computer program and apparatus toaccess data records that allows clients to access their personal datarecords and to receive updated information pertaining to their personalrecords information.

One example embodiment of the present inventive concept includes amethod or computer program that includes receiving a data file at a fileserver comprising client records information. The method may alsoinclude forwarding the file to a database and adding the file to arecord in the database. The method may further include creating adatabase file and storing the database file on the file server. Themethod may also include scheduling a call to at least one client, thecall including a portion of the information included in the receiveddata file. The method may further provide performing the call to the atleast one client, and monitoring the call to determine if any additionalinformation is provided from the at least one client during the courseof the call. The method may also include updating the client recordsinformation stored in the database based on the additional informationprovided by the at least one client.

Another example embodiment of the present inventive concept may alsoinclude an apparatus that includes a file server configured to accessclient data records. The file server may include a receiver configuredto receive a data file at the file server comprising client recordsinformation, and a transmitter configured to transmit the file to adatabase where the file is added to a record in the database. The fileserver may also include a processor configured to create a database fileand storing the database file on the file server, schedule a call to atleast one client, the call including a portion of the informationincluded in the received data file, perform the call to the at least oneclient, monitor the call to determine if any additional information isprovided from the at least one client during the course of the call, andupdate the client records information stored in the database based onthe additional information provided by the at least one client.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a conventional data record accessing system.

FIG. 2 illustrates an example data record accessing system according toan example embodiment of the present inventive concept.

FIG. 3 illustrates another example data record accessing systemaccording to another example embodiment of the present inventiveconcept.

FIG. 4 illustrates a flow diagram according to illustrates an exampleembodiment of the present inventive concept.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIG. 2 illustrates a data record accessing system 10B according to anexample embodiment of the present inventive concept. Referring to FIG.2, client 100 uses a web posting application to connect to a filetransfer protocol (FTP) application server 110 over a networkillustrated by the network cloud that may represent a wide area network,the Internet, etc. Once a connection is established, the client 100 maysend a data file to the FTP post server 110 (which may also include asecure shell (SSH) application).

The data file is originally sent to the FTP post server 110 whichprovides a connection to a file server 112. After the file has beenmoved to the file server 112, a record is generated based on thereceived file, and that record is sent to a database server, such as,for example, a SQL server 113. The SQL server 113 receives the data fileand a record may be generated and added to the SQL database in the SQLserver 113.

The file server 112 includes multiple server engines, which include aparser server engine 112A, an image parser engine 112B, a pre-builderengine 112C, a reporter engine 112D and a call builder engine 112E. Thefile server 112 may store VCE voice files and a CallQ.DBF file 112G inits internal memory. Operations performed by file server 112 may includecreation and updating of scheduling lists, auto scheduling of clientapplications and appointments, storing and accessing of common filesassociated with client information, creating and accessing of customfolders, and reporting of assets to clients.

The file server engines 112A-112E provide additional features forprocessing the data files which are sent to the file server 112. Forexample, parser server 112A may read and write the data files to the SQLcluster at the SQL server 113. The parser server 112A may also parseinformation for the client, such as, appointment data, and then formatthe appointment data for storage in appointment tables. The schedulebuilder 112B reviews schedules of clients and builds a record filedatabase file (i.e., CallQ.dbf file 112G).

The pre-builder 112C builds the voice files (VCE files) for the clients'records so that the clients may access their records and listen to thevoice files corresponding to their records. The pre-builder 112C alsoperforms a query for the scheduled call information that is setup by theschedule builder 112B. The pre-builder will then create a new file buildon the file server 112 for client access and for future updates.

The file server 112 may provide certain applications, such as, automaticscheduling of client appointment times, storing and accessing of commonfiles needed for client resources, creating and updating of customfolders for client resources, etc. The file server 112 may also providea reporter engine 112E that reports resources to other components of thedata accessing system 10B and to the clients. Voice data may be accessedfrom the VCE voice files 112F and other information may be accessed fromthe database file CallQ.dbf 112G.

One example operation of the data accessing system 10B is discussed indetail below. Next generation future phone calls are created at thetelephone server 117. Each of the telephone server lines will accessanother database file Schlist.dbf to determine schedule information forclients. The database file Schlist.dbf is also used to associate clientinformation with the future calls and to access the existing file buildin the file server 112 and/or create a new file build. Additionally, ifdata for a future call is not built on an existing file build, then, thecall may be built on the file telephone server 117.

The calls may then be made to a corresponding set of pre-establishedclients informing them of their personal information, scheduleinformation, etc. The telephone server 117 may then initiate the callsto the client telephones or call accessing stations (i.e., mobilestations). Once the calls are dialed out, the calls may be furthermonitored by the telephone server 117 to track the calls progress.During the calls, the call status may be updated periodically and thecall status information may be in the CallQ.dbf file 112G on the fileserver 112.

The reporter engine 112D will query the schedule lists, discover theschedules that are complete and the corresponding client reports thatare ready to be sent to the clients. Other operations of the reporterengine 112D may include inserting the record into the SQL server 113,which may offer a Histran application and an email queue service. Thefiles that are ready to be transferred to clients are placed in anexport file in the file server 112. The export files are then sent viaFTP, SSH, email, autodial applications, fax or a web posting applicationto the clients. In one example, the emails may be sent in bulk to thevarious clients in email notifications sent from the email server 116.The FTP server 110 provides a file transfer protocol application thatprovides easy access to the clients' records.

FIG. 3 illustrates a data record accessing system 10C according toanother example embodiment of the present inventive concept. Referringto FIG. 3, client 100 uses a web posting application to connect to webserver 120 over a network illustrated by the network cloud that mayrepresent a wide area network, the Internet, etc. Once a connection isestablished, the client 100 may send a data file to the web server 120.

The data file is originally sent to the web 120 which provides aconnection to a file server 112. After the file has been moved to thefile server 112, a record is generated based on the received file, andthat record is sent to a database server, such as, for example, a SQLserver 113. The SQL server 113 receives the data file and a record maybe generated and added to the SQL database in the SQL server 113.

The file server 112 includes multiple server engines, which include aparser server engine 112A, an image parser engine 112B, a pre-builderengine 112C, a reporter engine 112D and a call builder engine 112E. Thefile server 112 may store VCE voice files and a CallQ.DBF file 112G inits internal memory. Operations performed by file server 112 may includecreation and updating of scheduling lists, auto scheduling of clientapplications and appointments, storing and accessing of common filesassociated with client information, creating and accessing of customfolders, and reporting of assets to clients.

The file server engines 112A-112E provide additional features forprocessing the data files which are sent to the file server 112. Forexample, parser server 112A may read and write the data files to the SQLcluster at the SQL server 113. The parser server 112A may also parseinformation for the client, such as, appointment data, and then formatthe appointment data for storage in appointment tables. The schedulebuilder 112B reviews schedules of clients and builds a record filedatabase file (i.e., CallQ.dbf file 112G).

The pre-builder 112C builds the voice files (VCE files) for the clients'records so that the clients may access their records and listen to thevoice files corresponding to their records. The pre-builder 112C alsoperforms a query for the scheduled call information that is setup by theschedule builder 112B. The pre-builder will then create a new file buildon the file server 112 for client access and for future updates.

In another example, pre-scheduled intervals may be used to perform thevarious operations of file server 112. For example, the parser server112A may operate between 12 AM and 3 PM, the schedule builder 112B mayoperate at mid-day after 3 PM until early evening, and the reporter 112Dmay finalize and send out reports in the evening so that the clients arereminded of their next-day obligations the evening before theirappointments.

The file server 112 may provide certain applications, such as, automaticscheduling of client appointment times, storing and accessing of commonfiles needed for client resources, creating and updating of customfolders for client resources, etc. The file server 112 may also providea reporter engine 112E that reports resources to other components of thedata accessing system 10C and to the clients. Voice data may be accessedfrom the VCE voice files 112F and other information may be accessed fromthe database file CallQ.dbf 112G. One or more of these operations may beperformed with foxpro and/or other data customization softwareapplications.

One example operation of the data accessing system 10C is discussed indetail below. Next generation future phone calls are created at thetelephone server 117. Each of the telephone server lines will accessanother database file Schlist.dbf to determine schedule information forclients. The database file Schlist.dbf is also used to associate clientinformation with the future calls and to access the existing file buildin the file server 112 and/or create a new file build. Additionally, ifdata for a future call is not built on an existing file build, then, thecall may be built on the file telephone server 117.

The calls may then be made to a corresponding set of pre-establishedclients informing them of their personal information, scheduleinformation, etc. The telephone server 117 may then initiate the callsto the client telephones or call accessing stations (i.e., mobilestations). Once the calls are dialed out, the calls may be furthermonitored by the telephone server 117 to track the calls progress.During the calls, the call status may be updated periodically and thecall status information may be in the CallQ.dbf file 112G on the fileserver 112.

The reporter engine 112D will query the schedule lists, discover theschedules that are complete and the corresponding client reports thatare ready to be sent to the clients. Other operations of the reporterengine 112D may include inserting the record into the SQL server 113,which may offer a Histran application and an email queue service. Thefiles that are ready to be transferred to clients are placed in anexport file in the file server 112. The export files are then sent viaemail, autodial applications, fax or a web posting application to theclients. In one example, the emails may be sent in bulk to the variousclients in email notifications sent from the email server 116. The webserver 120 provides a web portal application that provides easy accessto the clients' records.

Another example embodiment of the present inventive concept isillustrated in FIG. 4. Referring to FIG. 4, operations of the data fileaccessing configuration may include receiving a data file at a fileserver comprising client records information (operation 401). Otheroperations may include forwarding the file to a database and adding thefile to a record in the database, (operation 402), creating a databasefile and storing the database file on the file server (operation 403),and scheduling a call to at least one client, the call including aportion of the information included in the received data file (operation404). Further operations may include performing the call to the at leastone client (operation 405), monitoring the call to determine if anyadditional information is provided from the at least one client duringthe course of the call (operation 406), and updating the client recordsinformation stored in the database based on the additional informationprovided by the at least one client (operation 407).

The present inventive concept is preferably realized in a hardwaredevice, such as, a computer, cellular phone, or other mobile terminaldevice etc. In other embodiments, the present invention may be realizedin hardware, software, firmware or a combination of hardware, softwareand/or firmware.

The above example embodiments may also be implemented in software codeand may be stored on a computer readable medium, such as, for example,non-volatile memory devices (e.g., RAM, ROM, hard disk etc.). Thesoftware code may be accessed from the computer readable medium and maybe executed by a processor. The executed program may provide one or moreof the features of the example embodiments.

While preferred embodiments of the present invention have beendescribed, it is to be understood that the embodiments described areillustrative only and the scope of the invention is to be defined solelyby the appended claims when considered with a full range of equivalentsand modifications (e.g., protocols, hardware devices, software platformsetc.) thereto.

What is claimed is:
 1. A method, comprising: receiving a data file froma client at a file server comprising client records information of theclient; parsing information for the client including appointment data bya parsing engine, and formatting the appointment data for storage in oneor more appointment tables; scheduling, by a schedule builder, a call toat least one client, the call including a portion of the information ofthe client included in the received data file, wherein the schedulebuilder reviews appointment data in the one or more appointment tablesand builds one or more schedule lists; building a voice file using theportion of the information so that the at least one client may accesstheir respective record and listen to the voice file corresponding totheir respective record; and sending the voice file including theportion of the information to the at least one client over the scheduledcall, wherein the voice file is sent by a reporter engine; wherein theparsing engine, schedule builder and reporting engine operate on a dailycycle such the parser engine operates for a first time period during theday, the schedule builder operates for a second time period, and thereporter engine operates for a third time period after the second timeperiod; wherein an export file on the file server is created based on alist of scheduled information that is determined to be a completed listof the scheduled information by the file server.
 2. The method of claim1, wherein the data file is transferred from the at least one client toat least one of an FTP server and a SSH server prior to said data filebeing received at the file server.
 3. The method of claim 1, wherein thedata file is transferred from the at least one client to a web serverprior to said data file being received at the file server.
 4. The methodof claim 1, comprising at least one of: forwarding the file to adatabase and adding the file to a record in the database; creating adatabase file and storing the database file on the file server; andupdating the client records information stored in the database based onupdated client information provided by the at least one client.
 5. Themethod of claim 4, wherein the database is a SQL server database.
 6. Themethod of claim 1, wherein the call is at least one of a dialed call, anemail, a text message and a fax.
 7. The method of claim 1, wherein thecall is transferred via at least one FTP and SSH.
 8. A non-transitorycomputer readable medium storing a software program that when executedcontrols a processor to perform: receiving a data file from a client ata file server comprising client records information; parsing informationfor the client including appointment data and formatting the appointmentdata for storage in one or more appointment tables; scheduling a call toat least one client, the call including a portion of the information ofthe client included in the received data file, wherein the schedulingcomprises reviewing appointment data in the one or more appointmenttables and building one or more schedule lists; building a voice fileusing the portion of the information so that the at least one client mayaccess their respective record and listen to the voice filecorresponding to their respective record; and sending the voice fileincluding the portion of the information the voice file to the at leastone client over the scheduled call, wherein the voice file is sent by areporter engine; wherein the parsing, scheduling and reporting engineoperate on a daily cycle such the parsing operates for a first timeperiod during the day, the scheduling operates for a second time period,and the reporter engine operates for a third time period after thesecond time period; wherein an export file on the file server is createdbased on a list of scheduled information that is determined to be acompleted list of the scheduled information by the file server.
 9. Thenon-transitory computer readable medium of claim 8, wherein the datafile is transferred from the at least one client to at least one of anFTP server and a SSH server prior to said data file being received atthe file server.
 10. The non-transitory computer readable medium ofclaim 8, wherein the data file is transferred from the at least oneclient to a web server prior to said data file being received at thefile server.
 11. The non-transitory computer readable medium of claim 8,wherein the processor is further configured to perform: forwarding thefile to a database and adding the file to a record in the database;creating a database file and storing the database file on the fileserver; and updating the client records information stored in thedatabase based on updated client information provided by the at leastone client.
 12. The non-transitory computer readable medium of claim 11,wherein the database is a SQL server database.
 13. The non-transitorycomputer readable medium of claim 8, wherein the call is at least one ofa dialed call, an email, a text message and a fax.
 14. Thenon-transitory computer readable medium of claim 8, wherein the call istransferred via at least one FTP and SSH.
 15. A server, comprising: areceiver configured to receive a data file from a client at the fileserver comprising client records information; and a processor configuredto parse information for the client including appointment data andformat the appointment data for storage in one or more appointmenttables, schedule a call to at least one client, the call including aportion of the information of the client included in the received datafile wherein the scheduling comprises reviewing appointment data in theone or more appointment tables and building one or more schedule lists,build a voice file using the portion of the information so that the atleast one client may access their respective record and listen to thevoice file corresponding to their respective record, send the voice fileincluding the portion of the information to the at least one client overthe scheduled call wherein the voice file is sent by a reporter engine,wherein the parsing, scheduling and reporting engine operate on a dailycycle such the parsing operates for a first time period during the day,the scheduling operates for a second time period, and the reporterengine operates for a third time period after the second time period;wherein an export file on the file server is created based on a list ofscheduled information that is determined to be a completed list of thescheduled information by the file server.
 16. The file server of claim15, wherein the data file is transferred from the at least one client toat least one of an FTP server and a SSH server prior to said data filebeing received at the file server.
 17. The file server of claim 15,wherein the data file is transferred from the at least one client to aweb server prior to said data file being received at the file server.18. The file server of claim 15, wherein the call is transferred via atleast one FTP and SSH.